Systems and methods for managing electronic tip data to provide merchant reviews

ABSTRACT

The disclosed embodiments provide systems, methods, and techniques for managing merchandising cards. A merchandising card may be, for example, a gift card, loyalty card, or the like. Consistent disclosed embodiments, a system for managing merchandising cards may include one or more memory devices storing instructions and one or more processors configured to acquire, from a device over a network, a plurality of locations associated with the device, the device locations being acquired at different instances in time within a predetermined period of time. Additionally, the processor may be configured to calculate a merchant confidence rating for a merchant using the device locations. Further, the one or more processors may be configured to, based on the merchant confidence rating, determine that the merchant matches a merchant that is associated with merchandising card, and send a reminder a user of the device.

TECHNICAL FIELD

The disclosed embodiments generally relate to systems and methods forelectronic recommendation systems and, more particularly, to systems andmethods for managing electronic tip data to provide reviews.

BACKGROUND

When deciding whether to visit a merchant, a customer often relies onreviews from previous customers of a merchant. Typically, a customervisits a review website and/or utilizes a software solution to searchfor goods or services and reads reviews associated with particularmerchants. In some instances, these websites may also rank the merchantsusing previous customer reviews.

However, solutions relying on customer reviews are problematic. Customerreviews are subjective, based on the customers' feelings towards themerchant. Subjective reviews are problematic because users often rateand judge merchants on individualistic scales, which are hard to compare(e.g., one user's four-star review may be equivalent to another user'sthree-star review). Subjective customer reviews may also lead toinaccurate overall reviews for a merchant or affect the merchant'srankings. Customers who feel negatively towards a merchant may be moremotivated to provide a review than customers who feel positively towardsa merchant.

In addition, the customer reviews are often stale. A customer does nothave the option to distinguish between an old review and a new review.Thus, merchants may be ranked unfairly. Moreover, these softwaresolutions often do not have the ability to acquire customer reviews inreal-time. And, even if these software solutions do attempt to acquirethe customer reviews in real-time, customers often do not provide areview because they are preoccupied. But, even further, if thesesoftware solutions do acquire the customer reviews in real-time, theyoften acquire customer reviews that are inconsistent with a customer'sactual experience with the merchant because the customer is usuallyengaged with the merchant and/or other activities when providing thereview in real-time.

In view of these and other shortcomings and problems with existingsystems, improved systems and techniques for managing electronic tipdata to provide reviews are desirable.

SUMMARY

In the following description, certain aspects and embodiments of thepresent disclosure will become evident. It should be understood that thedisclosure, in its broadest sense, could be practiced without having oneor more features of these aspects and embodiments. It should also beunderstood that these aspects and embodiments are merely exemplary.

The disclosed embodiments address disadvantages of existing systems byproviding novel systems, methods, and techniques for providingelectronic tip recommendations. Unlike prior implementations, thedisclosed systems and methods provide novel technical solutions thatprovide recommendations using objective customer review data (e.g., tipdata). The disclosed systems and methods, for example, provide anefficient, open, and fresh (e.g., a system that does not use stale data)system that provides recommendations using objective customer reviewdata.

In aspects of the disclosed embodiments, a system is disclosed. Thesystem may have one or more memory devices storing instructions and oneor more processors configured to execute instructions to, in response toreceiving information associated with a transaction card used tocomplete a transaction at a merchant associated with a merchant system:receive, from the merchant system, authorization data, the authorizationdata associated with the transaction, receive, from the merchant system,posted transaction data, the posted transaction data corresponding tothe authorization data, and in response to receiving the authorizationdata and posted transaction data: retrieve merchant review data for themerchant, determine a tip amount associated with the transaction basedon the authorization data and the transaction data, retrieve historicaltip data associated with the user, the historical tip data comprisinghistorical tip amounts, normalize the historical tip data, determine auser sentiment value for the merchant based on the normalized historicaltip amounts, the user sentiment value representing a user sentiment forthe particular merchant, modify the merchant review data based on theuser sentiment, and provide the merchant review data to a consumersystem,

Aspects of the disclosed embodiments may also include a non-transitorytangible computer-readable medium that stores software instructionsthat, when executed by one or more processors, are configured for andcapable of performing and executing one or more of the methods,operations, and the like consistent with disclosed embodiments. It is tobe understood that both the foregoing general description and thefollowing detailed description are exemplary and explanatory only, andare not restrictive of the disclosed embodiments as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate disclosed embodiments and,together with the description, serve to explain the disclosedembodiments. In the drawings:

FIG. 1 is a block diagram of an exemplary system environment, consistentwith disclosed embodiments;

FIG. 2 is a block diagram of an exemplary user device, consistent withdisclosed embodiments;

FIG. 3 is a block diagram of an exemplary computer system, consistentwith disclosed embodiments;

FIG. 4 is a flowchart of an exemplary merchant review capturing process,consistent with disclosed embodiments;

FIG. 5 is a flowchart of an exemplary merchant review modificationprocess, consistent with disclosed embodiments;

FIG. 6 is a flowchart of an exemplary merchant review capturing process,consistent with disclosed embodiments; and

FIG. 7 is a flowchart of an exemplary recommendation provisioningprocess, consistent with disclosed embodiments.

DETAILED DESCRIPTION

Generally, the disclosed embodiments are directed to systems and methodsfor electronic recommendation systems and, more particularly, to systemsand methods for managing electronic tip data to provide reviews.

The term “transaction card,” as used herein, may refer to a physical ordigital card product that includes features to facilitate a financial orother type of transaction information. Examples of transaction cardsinclude, but are not limited to, credit cards, debit cards, gift cards,rewards cards, frequent flyer cards, merchant-specific cards, discountcards, identification cards, membership cards, and driver's licenses.The physical properties of a physical transaction card (e.g., size,flexibility, location of various components included in the card) maymeet the various international standards, including, for example,ISO/IEC 7810, ISO/IEC 7811, ISO/IEC 7812, ISO/IEC 7813, ISO/IEC 7816,ISO 8583, ISO/IEC 4909, and ISO/IEC 14443. For example, a transactioncard may have a dimension of 85.60 mm (width) by 53.98 mm (height) by0.76 mm (thickness), as specified in ISO/ICE 7810. A transaction cardmay also be digital. That is, details (i.e., transaction accountdetails) used to process a transaction card may be stored digitally on adevice embedded in the card, and the device may send these details to amerchant's payment system. Both physical and digital transaction cardsmay be associated with a transaction account. The transaction accountmay be provided to a user by a financial institution.

A “merchant,” as used herein, may include any company, business,individual, or charity that conducts any type of transactions. Forexample, a merchant may be a retailer, a financial service provider, anautomotive dealer, a software provider, or the like. In someembodiments, the merchant may sell an item or service from a merchantlocation. This merchant location may be a physical location (i.e.,brick-and-mortar location) or a virtual (online) location.

A “user” (i.e., a “customer”), as used herein, may be any entity thatbuys an item or service from a merchant. In some embodiments, a user mayuse a transaction account to buy goods or services from the merchant. Auser may provide reviews of merchants associated with merchant systems.Throughout this disclosure, the terms “user,” “customer,” and “consumer”may be used interchangeably. In some embodiments, users may also havethe ability to upload their electronic or physical transaction card to asystem environment, such as a system environment associated with afinancial service provider. In some embodiments, components of thesystem environment may be implemented in an application that isinstalled on a user's mobile device.

Reference will now be made in detail to exemplary embodiments, examplesof which are illustrated in the accompanying drawings and disclosedherein. Wherever convenient, the same reference numbers will be usedthroughout the drawings to refer to the same or like parts.

FIG. 1 shows a block diagram of an exemplary system environment 100,consistent with disclosed embodiments. The components and arrangementsshown in FIG. 1 are not intended to limit the disclosed embodiments, asthe components used to implement the disclosed processes and featuresmay vary.

In accordance with disclosed embodiments, system environment 100 mayinclude one or more user devices 110, merchant systems 120, financialservice provider systems 130, consumer systems 140, networks 150,databases 160, and cloud services 170. Other components known to one ofordinary skill in the art may be included in system environment 100 togather, process, transmit, receive, acquire, and provide informationused in conjunction with the disclosed embodiments. In addition, systemenvironment 100 may further include other components that perform orassist in the performance of one or ore processes that are consistentwith disclosed embodiments.

A customer may operate a client device or user device 110, which may bea desktop computer, a laptop computer, a tablet, a smartphone, asmartwatch, a pair of multifunctional glasses, a tracking device, or anysuitable device with computing capability. User device 110 may comprisea memory, a processor, and/or other specialized hardware that isconfigured to execute one or more methods of the disclosed embodiments.User device 110 may have an application installed thereon, which mayenable user device 110 to communicate with merchant system 120,financial service provider system 130, and/or consumer system 140 vianetwork 150. Alternatively, user device 110 may connect to consumersystem 140, financial service provider system 130 and/or merchant system120 through use of web browser software.

User device 110 may allow a user to access information stored infinancial service provider system 130, such as, for example, financialinformation related to recent purchase transactions, financialdiscounts, financial statements, account information, transactionaccount information, and/or the like. User device 110 may also include aGPS unit (not pictured). In some embodiments, user device 110 may usethe GPS unit to acquire and transmit the position information, such asthe physical location of user device 110, to merchant system 120 and/orfinancial service provider system 130. An exemplary computer systemconsistent with user device 110 is discussed in additional detail withrespect to FIG. 2.

A user may operate user device 110 to perform one or more operationsconsistent with disclosed embodiments. In one aspect, a user may be acustomer of a financial service provider that may be associated withfinancial service provider system 130. For instance, a financial serviceprovider may maintain a financial service account (e.g., credit cardaccount) for the customer that the customer may use to purchase goodsand/or services online or at brick-and-mortar locations associated witha merchant, In another aspect, a user may also be a customer of amerchant that is associated with merchant system 120. For instance, auser may operate user device 110 to initiate purchase transactions witha merchant via merchant system 120 and receive communications associatedwith a transaction account. Additionally, in certain embodiments, a usermay operate user device 110 to view a financial service account orfinancial statement provided by a financial service provider orfinancial service provider system 130.

Merchant system 120 may be a computing system that is associated with amerchant or other business entity such as a retailer, a grocery store, aservice provider (e.g., utilities, etc.), or any other type of entitythat provides goods and/or services that customers may purchase. Whilesystem environment 100 is shown in FIG. 1 with one merchant system 120,the disclosed embodiments may be implemented in a system including twoor more merchant systems 120 associated with any number of underlyingbusiness entities. Further, merchant system 120 is not limited toconducting business in any particular industry or field,

Merchant system 120 may be associated with a merchant brick-and-mortarlocation that a user may physically visit to purchase goods and/orservices from a merchant. Merchant systems 120 may include computingdevices that perform financial service transactions with customers(e.g., Point of Sale (POS) terminals, kiosks, etc.). Merchant system 120may also include back-end and/or front-end computing components thatstore data and execute software instructions to perform operationsconsistent with disclosed embodiments, such as computers that areoperated by employees of the merchant (e.g., back-office systems, etc.).Merchant system 120 may also be associated with a merchant that providesgoods and/or services via known online or e-commerce type of solutions.For example, such a merchant may sell goods via a website using knownonline or e-commerce systems and solutions to market, sell, and processonline transactions.

In some embodiments, merchant system 120 may include one or more serversor other type of computing devices configured to execute softwareinstructions stored in memory to perform one or more processesconsistent with disclosed embodiments. Merchant system 120 may alsoinclude one or more memory devices storing data and softwareinstructions and one or more processors configured to use the data andexecute the software instructions to perform server-based functions andoperations known to those skilled in the art, In some embodiments,merchant system 120 may have an application installed thereon to performone or more processes that are consistent with disclosed embodiments.

In certain embodiments, merchant system 120 may further include serversthat are configured to execute stored software instructions to performoperations associated with a merchant, including processes associatedwith handling purchase transactions, generating transaction data, andgenerating product data (e.g., SKU data) relating to purchasetransactions, etc. Merchant system 20 may be embodied in one or moreservers that may be a general-purpose computer, a mainframe computer, orany combination of these components. In certain embodiments, merchantsystem 120 (or a system including merchant system 120) may be configuredas an apparatus, system, and the like, based on the storage, execution,and/or implementation of the software instructions that perform one ormore operations consistent with disclosed embodiments. Merchant system120 may be standalone or part of a subsystem included in a largersystem. For example, merchant system 120 may include distributed serversthat are remotely located and communicate over network 150. An exemplarycomputer system consistent with merchant system 120 is discussed inadditional detail with respect to FIG. 3.

Financial service provider system 130 may be a system associated with afinancial service provider (not shown), such as a bank, a credit cardcompany, a lender, brokerage firm, or any other type of financialservice entity that generates, provides, manages, maintains transactionaccounts (e.g., financial service accounts), manages transaction cards,etc., for customers. Financial service provider system 130 may be one ormore computing systems that are configured to execute softwareinstructions stored on one or more memory devices to perform operationsconsistent with disclosed embodiments. For example, financial serviceprovider system 130 may include memory devices storing data and softwareinstructions and processors configured to use the data and execute thesoftware instructions to perform server-based functions and operationsknown to those skilled in the art. Financial service provider system 130may include one or more general-purpose computers, mainframe computers,or any combination of these types of components. In some embodiments,financial service provider system 130 may have an application installedthereon to perform processes that are consistent with disclosedembodiments.

In certain embodiments, financial service provider system 130 may beconfigured as a particular apparatus, system, and the like, based on thestorage, execution, and/or implementation of the software instructionsthat perform operations consistent with disclosed embodiments. Financialservice provider system 130 may be standalone, or it may be part of asubsystem included in a larger system. For example, financial serviceprovider system 130 may include distributed servers that are remotelylocated and communicate over network 150 or a dedicated network of afinancial service provider. An exemplary computing system consistentwith financial service provider system 130 is discussed in additionaldetail with respect to FIG. 3, below.

Financial service provider system 130 may include or may access one ormore storage devices configured to store data and/or softwareinstructions used by one or more processors of financial serviceprovider system 130 to perform operations consistent with disclosedembodiments. For example, financial service provider system 130 mayinclude memory configured to store one or more software programs thatperform several functions when executed by a processor. The disclosedembodiments are not limited to separate programs or computers configuredto perform dedicated tasks. For example, financial service providersystem 130 may include memory that stores a single program or multipleprograms. Additionally, financial service provider system 130 mayexecute one or more programs located remotely from financial serviceprovider system 130. For example, financial service provider system 130may access one or more remote programs stored in memory included with aremote component that, when executed, perform operations consistent withdisclosed embodiments. In certain aspects, financial service providersystem 130 may include server software that generates, maintains, andprovides services associated with managing tip data to provide reviews.In other aspects, financial service provider system 130 may connectseparate servers or similar computing devices that generate, maintain,and provide services associated with financial data for a financialservice provider associated with financial service provider system 130.

In some embodiments, financial service provider system 130 may use amodel to calculate a score, consistent with embodiments of the presentdisclosure. For example, the model may include convolutional neuralnetworks that determine attributes in user and/or merchant informationbased on features extracted from user and/or merchant information, Invarious aspects, the models may include statistical algorithms todetermine a score, such as a commonality score. For example, models mayinclude regression models that estimate the relationships among inputand output variables. In some aspects, the models may additionally sortelements of a dataset using classifiers to determine the probability ofa specific outcome. Statistical identification models may be parametric,non-parametric, and/or semi-parametric models. A convolutional neuralnetwork model can be configured to process the user and/or merchantinformation into a collection of features. The convolutional neuralnetwork can comprise an input layer, one or more middle layers, and oneor more output layers. In some aspects, each middle layer and the outputlayer can be a deterministic function of the values of the precedinglayer. The convolutional neural network can include one or moreconvolutional layers. Each convolutional layer can be configured toconvolve one or more spatial filters with the convolutional layer inputto generate a convolutional layer output tensor. In some embodiments,the convolutional neural network can also include pooling layers andfully connected layers according to methods known in the art. In someaspects, the convolutional neural network may be a reinforcementlearning model. Models may also include Random Forests composed of acombination of decision tree predictors. Such decision trees maycomprise a data structure mapping observations about something, in the“branch” of the tree, to conclusions about that thing's target value, inthe “leaves” of the tree. Each tree may depend on the values of a randomvector sampled independently and with the same distribution for alltrees in the forest. Models may additionally or alternatively includeclassification and regression trees, or other types of models known tothose skilled in the art.

Consumer system 140 may be a computing system that bridges togethermerchants and customers. In fact, in some embodiments, consumer systemmay be a merchant system. Consumer system 140 may provide customerreviews (e.g., reviews made users associated with user device 110)concerning one or more merchants (e.g., merchants associated withmerchant system 120). Customer system 140 may host a website or the likethat may be access by user device 110, merchant system 120, and/orfinancial service provider system 130 via network 150,

Consumer system 140 may include one or more servers or another type ofcomputing device configured to execute software instructions stored inmemory to perform one or more processes consistent with disclosedembodiments. For example, consumer system 140 may include one or morememory devices storing data and software instructions and one or moreprocessors configured to use the data and execute the softwareinstructions to perform server-based functions and operations known tothose skilled in the art. In some embodiments, Consumer system 140 mayhave an application installed thereon to perform one or more processesthat are consistent with disclosed embodiments.

Consumer system 140 may further include servers that are configured toexecute stored software instructions to perform operations associatedwith a consumer, including processes associated with handling purchasetransactions, generating transaction data, generating product data(e.g., SKU data) relating to purchase transactions, generating merchantreview data (e.g., recommendation data), etc. Consumer system 140 mayinclude one or more servers that may be a general-purpose computer, amainframe computer, or any combination of these components. In certainembodiments, Consumer system 140 (or a system including consumer system140) may be configured as an apparatus, system, and the like, based onthe storage, execution, and/or implementation of the softwareinstructions that perform one or more operations consistent withdisclosed embodiments. In some embodiments, consumer system 140 maytransmit data to one or more user device(s) 110.

Consumer system 140 may be standalone or part of a subsystem included ina larger system. For example, consumer system 140 may includedistributed servers that are remotely located and communicate over anetwork (e.g., network 150 or a local network). An exemplary computingdevice consistent with consumer system 140 is discussed in additionaldetail with respect to FIG. 3.

Network 150 may comprise any computer networking arrangement used toexchange data. For example, network 150 may be the Internet, a privatedata network, a virtual private network (VPN) using a public network,and/or other suitable connections that enable the components of systemenvironment 100 to send and acquire information. Network 150 may alsoinclude a public switched telephone network (“PSTN”) and/or a wirelessnetwork such as a cellular network, wired Wide Area Network, Wi-Finetwork, or other known wireless network (e.g., WiMAX) capable ofbidirectional data transmission. In some embodiments, network 150 maycomprise one or more local networks. A local network may comprise anytype of computer networking arrangement used to exchange data in alocalized area, such as Wi-Fi based on IEEE 802.11 standards,Bluetooth™, Ethernet, and other suitable network protocols that enablecomponents of system environment 100 to interact with one another and toconnect to network 150 for interacting with components in systemenvironment 100. In some embodiments, a local network may be a portionof network 150. In other embodiments, components of system environment100 may communicate via network 150 without a separate local network.

Database 160 may include one or more memory devices that storeinformation. By way of example, database 160 may include Oracle™databases, Sybase™ databases, or other relational databases ornon-relational databases, such as Hadoop sequence files, HBase™, orCassandra™. The databases or other files may include, for example, dataand information related to the source and destination of a networkrequest, the data contained in the request, etc. Systems and methods ofdisclosed embodiments, however, are not limited to separate databases.Database 160 may include computing components (e.g., database managementsystem, database server, etc.) configured to acquire and processrequests for data stored in memory devices of database 160 and toprovide data from database 160.

Cloud service 170 may include a physical and/or virtual storage systemassociated with cloud storage for storing data and providing access todata via a public network such as the Internet, Cloud service 170 mayinclude cloud services such as those offered by, for example, Amazon®,Apple®, Cisco®, Citrix®, IBM®, Joyent®, Google®, Microsoft®, Rackspace®,Salesforce.com®, and Verizon®/Terremark®, or other types of cloudservices accessible via network 150. In some embodiments, cloud service350 comprises multiple computer systems spanning multiple locations andhaving multiple databases or multiple geographic locations associatedwith a single or multiple cloud storage service(s). As used herein,cloud service 170 refers to physical and virtual infrastructureassociated with a single cloud storage service and may manage and/orstore data associated with managing tip data to provide reviews,

FIG. 2 shows a block diagram of an exemplary user device 110, consistentwith disclosed embodiments. In some embodiments, user device 110 mayhave one or more displays 210, input/output (I/O) devices 220,processors 230, memory device 240, programs 250, applications 252, datastorages 260, and cameras 270. User device 110 may be a desktopcomputer, a laptop, a tablet, a smartphone, a multifunctional watch, apair of multifunctional glasses, a tracking device, or any suitabledevice with computing capability. The components and arrangements shownin FIG. 2 are not intended to limit the disclosed embodiments, as thecomponents used to implement the disclosed processes and features mayvary.

Display 210 may be one or ore devices configured to communicate visualdata to a user of user device 110. For example, display 210 may be aThin Film Transistor Liquid Crystal Display (LCD), In-Place SwitchingLCD, Resistive Touchscreen LCD, Capacitive Touchscreen LCD, an OrganicLight Emitted Diode (OLED) Display, an Active-Matrix OrganicLight-Emitting Diode (AMOLED) Display, a Super AMOLED, a Retina Display,a Haptic or Tactile touchscreen display. In some embodiments, thedisplay 210 may be covered by a protective layer (not shown), such asGorilla Glass. In certain embodiments, display 210 may accept input froma user interacting with display 210.

I/O device 220 may be one or more devices configured to allow data to beacquired and/or transmitted by user device 110. I/O device 220 mayinclude one or more digital and/or analog communication devices thatallow user device 110 to communicate with other machines and devices,such as other components of system environment 100 shown in FIG. 1. Forexample, user device 110 may include interface components that mayprovide interfaces to one or more input devices, such as keyboards,mouse devices, and the like, which may enable user device 110 to acquireinput from an operator of financial service provider system 130 (FIG.1).

Processor 230 may include one or more known processing devices, such asa microprocessor from the Pentium™ or Xeon™ family manufactured byIntel™, the Turion™ family manufactured by AMD™, or any of variousprocessors manufactured by Sun Microsystems or other manufacturers.Processor 230 may constitute a single-core or multiple-core processorthat executes parallel processes simultaneously. For example, processor230 may be a single-core processor configured with virtual processingtechnologies. In certain embodiments, processor 230 may use logicalprocessors to simultaneously execute and control multiple processes.Processor 230 may implement virtual machine technologies, or other knowntechnologies to provide the ability to execute, control, run,manipulate, store, etc., multiple software processes, applications,programs, etc. In certain embodiments, processor 230 may include amultiple-core processor arrangement (e.g., dual, quad-core, etc.)configured to provide parallel processing functionalities to allow userdevice 110 to execute multiple processes simultaneously. One of ordinaryskill in the art would understand that other types of processorarrangements could be implemented that provide for the capabilitiesdisclosed herein. The disclosed embodiments are not limited to any typeof processor(s) configured in user device 110.

Memory device 240 may also store data that may reflect any type ofinformation in any format that the system may use to perform operationsconsistent with disclosed embodiments. Memory device 240 may storeinstructions to enable processor 230 to execute one or moreapplications, such as server applications, account managementapplications, network communication processes, and any other type ofapplication or software. Alternatively, the instructions, applicationprograms, etc., may be stored in an external storage (not shown) incommunication with user device 110 via network 150 or any other suitablenetwork. Memory device 240 may be a volatile or non-volatile, magnetic,semiconductor, tape, optical, removable, non-removable, or other type ofstorage device or tangible (i.e., non-transitory) computer-readablemedium.

Programs 250 executed by processor 230 may cause processor 230 toexecute one or more processes related to financial services provided tousers including, but not limited to, processing credit and debit cardtransactions, checking transactions, funding deposits and withdrawals,transferring money between financial accounts, lending loans, managingtransaction accounts, processing payments for credit card and loanaccounts, managing tip data to provide reviews. Programs 250 may alsocontain one or more applications 252 that specifically provide one ormore functionalities to manage transaction accounts and managing tipdata to provide reviews. Data storage 260 may store, for example,personal information, account information, display, settings, one ormore configurations, one or more logs, and preferences. Data storage 260may also store other data, such as client data or transaction data.

In some embodiments, camera 270 may include back side, front side, and awidth. Camera 270 may be made of various materials, including metal,silicon, plastic, or the like. The material composition of camera 270 isnot limited by this disclosure, Camera 270 may include multiple cameras,where the cameras may be enable user device 110 to capture images andvideo from a viewpoint of 360° without moving user device 110. In someembodiments, camera 270 may include front and rear-facing cameras.Camera 270 may utilize, via processor 230, one or more programs 250 toprovide the user with the functionality to take or record pictures andvideo and/or store the pictures and video in data storage 260.

FIG. 3 shows a block diagram of an exemplary computing system 300,consistent with disclosed embodiments, illustrating a computing systemconfiguration that may be associated with merchant system 120, and/orfinancial service provider system 130. In some embodiments, computingsystem 300 may have one or more processors 310, I/O devices 320, and/ormemory devices 330. The components and arrangements shown in FIG. 3 arenot intended to limit the disclosed embodiments, as the components usedto implement the disclosed processes and features may vary.

In some embodiments, computing system 300 may take the form of a server,a general-purpose computer, a mainframe computer, a laptop, asmartphone, a mobile device, or any combination of these components. Incertain embodiments, computing system 300 (or a system includingcomputing system 300) may be configured as a particular apparatus,system, and the like, based on the storage, execution, and/orimplementation of the software instructions that perform one or moreoperations consistent with disclosed embodiments. Computing system 300may be standalone, or it may be part of a subsystem included in a largersystem. Memory device 330 may be similar to memory device 240, asdescribed above, with the expectation that memory device 330 is used byand within computing system 300 instead of user device 110. Likewise,processor 310, I/O device 320, and program 336 may be similar toprocessor 230, I/O device 220, and programs 250, respectively.

In some embodiments, memory device 330 may include one or more storagedevices configured to store data and instructions used by processor 310to perform functions related to the disclosed embodiments. For example,memory device 330 may be configured with software instructions, such asprogram 336 that may perform operations when executed by processor 310.The disclosed embodiments are not limited to separate programs orcomputers configured to perform dedicated tasks. For example, memorydevice 330 may include a single program 336 that performs the functionsof computing system 300, or program 336 could comprise multipleprograms. Additionally, processor 310 may execute one or more programslocated remotely from computing system 300. For example, user device110, merchant system 120, and/or financial service provider system 130,may, via computing system 300 (or variants thereof), access one o oreremote programs that, when executed, perform functions related tocertain disclosed embodiments. Processor 310 may further execute one ormore programs located in database 160 and/or cloud service 170. In someembodiments, program 336 may be stored in an external storage device,such as at cloud service 170 located outside of computing system 300,and processor 310 may execute program 336 remotely.

Memory device 330 may also store data that may reflect any type ofinformation in any format that the system may use to perform operationsconsistent with disclosed embodiments. Memory device 330 may storeinstructions to enable processor 210 to execute one or moreapplications, such as server applications, account managementapplications, network communication processes, and any other type ofapplication or software. Alternatively, the instructions, applicationprograms, etc., may be stored in an external storage (not shown) incommunication with computing system 300 via network 150 or any othersuitable network, Memory device 330 may be a volatile or non-volatile,magnetic, semiconductor, tape, optical, removable, non-removable, orother type of storage device or tangible (i.e., non-transitory)computer-readable medium.

Memory device 330 may include transaction data 332. Transaction data 332may include information related to purchasing transactions initiated bya user. For example, transaction data may include a user identifier anda purchase price. The user identifier may be a credit or debit cardnumber, an account number, or other means of identifying the userinitiating the purchase transaction. The purchase price may include anumber representing the total sale price of the purchase transactionand/or may include a list of the various items purchased from themerchant. In some embodiments, merchant system 120 may collect,generate, and provide transaction data relating to purchase transactionsinvolving a user to financial service provider system 130. In someembodiments, merchant system 120 may further provide product data (e.g.,SKU data) and transaction data relating to purchase transactionsinvolving a user to financial service provider system 130. Merchantsystem 120 may provide this information to financial service providersystem 130 via network 150. In some embodiments, transaction data 332may be stored in database 160 and/or cloud service 170 or in externalstorage (not shown) in communication with computing system 300 vianetwork 150 or any other suitable network.

Memory device 330 may further include client data 334. Client data 334may include information about particular customers of the financialservice provider. For example, client data 334 may include customers'account information, debit or credit card information, history ofpurchase transactions, financial statements, credit score, risk profile,and/or transaction account data. Client data 334 may further contain oneor more user profiles associating the account information, debit orcredit card information, history of purchase transactions, financialstatements, credit score, risk profile, and/or transaction accountinformation, including stored transaction accounts. When a userinitiates a purchase transaction, processor 310 may analyze client data334 or user profiles before authorizing the purchase transaction onbehalf of a user. In some embodiments, client data 334 may be stored indatabase 160 and/or cloud service 170 or in external storage (not shown)in communication with computing system 300 via network 150 or any othersuitable network.

In some embodiments, processor 310 may analyze transaction data 332 inreference to client data 334. For example, processor 310 may analyzetransaction data to determine which client with information stored inclient information 334 is initiating the purchase transaction. Processor310 may access the particular user's client information to determinetheir account information, debit or credit card information, history ofpurchase transactions, financial statements, credit score, risk profile,and/or transaction account information.

As discussed above, financial service device 130 may include at leastone computing system 300. Further, it should be understood thatvariations of computing system 300 may be used by other components ofsystem environment 100, including merchant system 120. In someembodiments, computing system 300 may be a single server or may beconfigured as a distributed computer system including multiple serversor computers that interoperate to perform one or more of the processesand functionalities associated with the disclosed embodiments.

FIG. 4 is a flowchart of an exemplary merchant review capturing process400, consistent with disclosed embodiments. In some embodiments,financial service provider system 130 may perform some or all of thesteps of process 400. In certain embodiments, other components of systemenvironment 100 (e.g., user device 110, merchant system 120, consumersystem 140, etc.) may perform one or more steps of process 400. Forsimplicity, process 400 will be described below as being performed byfinancial service provider system 130.

At step 405, financial service provider system 130 may receiveauthorization data. Authorization data may include authorizationinformation corresponding to when a user attempts to and/or makes atransaction (e.g., a purchase, a payment, etc.) via merchant system 120(i.e. the current transaction). For example, when a user uses atransaction card or another payment method at merchant system 120 (e.g.,in the current transaction), authorization data may be created.Financial service provider system 130 may receive authorization datafrom merchant system 120, which may be associated with a merchant.Financial service provider system 130 may also receive authorizationdata from mobile device 110, consumer device 140, database 160, and/orcloud service 170. For example, financial service provider system 130may receive authorization data from mobile device 110 via an applicationinstalled on mobile device 110. For example, a user may use atransaction card, the user's device (such as user device 110) or otherpayment method at a restaurant to pay for a transaction (e.g. an orderfor a meal) through the restaurant's POS. The user may be required toenter a PIN or other passcode to approve and/or verify their identity.The authorization data from the transaction card or other payment methodis transmitted via the restaurant's POS to an authorizing entity, suchas financial service provider system 130. Financial service providersystem 130 receives the authorization data and approves or disapprovesthe transaction. Once a decision is made at the financial serviceprovider system 130, a return message is sent to the restaurant's systemindicating the approval or disapproval of the transaction.

The authorization information may include an authorization amount,information concerning a transaction card or other payment method that auser used to make the purchase, merchant information (e.g., a merchantname, a merchant address, a merchant account number, etc.) associatedwith a merchant, date information, time information, locationinformation, or the like. The authorization information may includepreliminary information, that is, information that is not final and/oris subject to change. For example, if financial service provider system130 is associated with a transaction card used by a user to make atransaction at merchant system 120, financial service provider system130 may initially deduct the authorization amount from an accountassociated with the transaction card but may eventually update thededucted amount before the transaction is finalized.

At step 410, financial service provider system 130 may receive postedtransaction data. Posted transaction data may include posted transactioninformation, such as a posted transaction amount, information concerninga transaction card or other payment method that a user used to make thepurchase, merchant information (e.g., a merchant name, a merchantaddress, a merchant account number, etc.) associated with a merchant,date information, time information, location information, or the like.In some embodiments, elements of he posted transaction data maycorrespond to elements of the authorization data.

The posted transaction information may, additionally or alternatively,comprise a tip amount. In certain embodiments, financial serviceprovider system 130 may calculate a tip amount using the authorizationdata and posted transaction data. Financial service provider system 130may calculate the tip amount by subtracting an authorization amount froma posted transaction amount. For example, if financial service providersystem 130 is associated with a transaction card used in the currenttransaction, financial service provider system 130 may modify a deductedauthorization amount with the posted transaction amount. The informationcontained in the posted transaction data may include finalizedinformation, that is, information that is final and/or not typicallysubject to change.

When a user uses a transaction card or another payment method atmerchant system 120 and the payment is accepted, posted transaction datamay be created. Financial service provider system 130 may receive postedtransaction data from merchant system 120, which may be associated witha merchant. Financial service provider system 130 may also receiveposted transaction data from mobile device 110, consumer device 140,database 160, and/or cloud service 170.

At step 415, financial service provider system 130 may retrieve merchantreview data. Merchant review data may indicate user sentiment towards amerchant. User sentiment may indicate how one or ore users feel aboutthe merchant and/or the merchant's goods, services, location, customerservice, or any other aspect associated with a merchant. Merchant reviewdata may indicate that a user feels that the merchant is excellent,good, average, below-average, poor, etc. In some embodiments, merchantreview data may include a rating, such as an excellent rating, a goodrating, an average rating, a below-average rate, a poor rating, or thelike.

Merchant review data may include and/or be represented by a percentage,a number, a star rating, any combination thereof, or the like.Additionally or alternatively, merchant review data may include and/orbe represented by a range of percentages, numbers, star ratings, anycombination thereof, or the like. In some embodiments, merchant reviewdata may contain objective data, that is, data based on numbers and/orfacts. For example, objective data may include data representative of atip provided by a customer to a merchant, a total amount that a customerspent at a merchant, a number of times a customer visited a merchantduring a particular time period, an elapse time between merchant visitsby the customer, a number of times that a customer visited a merchant'scompetitor, etc. Additionally, merchant review data may containsubjective data, that is, data based on, for example, the opinion of oneor more users.

In some embodiments, financial service provider system 130 may retrievemerchant review data in response to receiving the authorization data andposted transaction data (at steps 405 and 410, respectively). Financialservice provider system 130 may retrieve merchant review data frommerchant system 120, consumer system 140, database 160, and/or cloudservice 170. For example, financial service provider system 130 may senda request to consumer system 140 and receive merchant review data inresponse to sending the request. In some embodiments, financial providersystem 130 may send or receive the response from consumer system 140 viaan application programmable interface (API).

The retrieved merchant review data may be associated with theauthorization and/or posted transaction data. Additionally oralternatively, the retrieved merchant review data may be associated withmerchant review data generated by a user (e.g., the user making theinitial transaction with the merchant to produce the authorization data)and/or other users. The retrieved merchant data may be associated with aparticular merchant (e.g., a merchant associated with merchant system120). In some embodiments, the retrieved merchant data may represent theoverall user sentiment of the merchant (e.g., the user sentiment of aplurality of users).

At step 420, financial service provider system 130 may modify theretrieved merchant review data based on the authorization data and theposted transaction data. As discussed above, the retrieved merchantreview data may be associated with the user and/or other users.Accordingly, financial service provider system 130 may modify retrievedmerchant review data associated solely with the user or modify retrievedmerchant review data associated with the user and/or other users. In anyof the previous situations, financial service provider system 130 maymodify retrieved merchant review data using one or more steps asdescribed in FIG. 5.

For example, at step 505, financial service provider system 130 mayretrieve historical (e.g., previously processed) tip data associatedwith the user. In some embodiments, financial service provider system130 may retrieve the historical tip data from user device 110, consumerdevice 140, database 160, cloud service 170, or the like. Historical tipdata may include data that financial service provider system 130previously processed using one or more steps of FIG. 4.

Tip data may include tip information, such as a tip amount, merchantinformation, user information, authorization data, posted transactiondata, date information, time information, location information, and/orother information. The tip information may be associated with atransaction between the user and a merchant. Tip data may include one ormore sets of tip information, and each of the sets of tip informationmay correspond to a particular transaction made by the user. Forexample, tip data may include first tip information that corresponds toa first transaction and second tip information that corresponds to asecond transaction.

At step 510, financial service provider system 130 may select a portionof the historical tip data associated with the user. Financial serviceprovider system 130 may select the portion of the historical tip databased on a date range, a time range, or a range of locations (e.g., arange of GPS coordinates), and/or a location zone (e.g., an area insidea perimeter formed by GPS coordinates). In some embodiments, financialservice provider system 130 may select the portion of the historical tipdata based on one or more merchant attributes. Financial serviceprovider system 130 may select the portion of the historical tip databased on one or more merchant attributes associated with merchant of thecurrent transaction (e.g., merchant associated with merchant device120).

A merchant attribute may include, for example, a merchant category, amerchant rating, a service type, a merchant location category, amerchant geographic category, a customer demographic, a merchant costcategory, or any other attribute that may be associated with a merchant.A merchant category may describe a description of what the merchantsales, services, etc. For example, if the merchant is a restaurant, themerchant category may include descriptions such as “Burger Joint,”“Pizza Place,” “Chinese Establishment,” “Tex-Mex Restaurant,” etc. Asanother example, if the merchant is a repair shop, the merchant categorymay include descriptions such as “Electricity,” “HVAC,” “ComputerSystems,” etc.

Next, a merchant rating may include descriptions as described above(excellent, good, etc.) and/or relate to one or more user sentiments.Financial service provider system 130 may have determined a merchantreview that includes the merchant review rating by previously completingone or more steps of FIG. 4. Further, a service type may include adescription of a type of service provided by the merchant. For example,if the merchant is a restaurant, the service type may includedescriptions such as “Fine Dining,” “Five Star,” “Quick Service,” “FastFood,” etc. As another example, if the merchant is a repair shop, themerchant category may include descriptions “mobile services,” “on-call,”“24-hour,” etc. In addition, a merchant location category may correspondto a description that describes the physical or virtual location of themerchant. The descriptions may include, for example, “e-commerce,”“brick-and-mortar,” “mall location,” “highway location,” etc.

In some embodiments, a merchant location may be different from amerchant geographic category. A merchant geographic category may be adescription that denotes the position of the merchant geographically.For example, these descriptions may include “Southern U.S.,”“Asia-Pacific,” “Nigeria,” “Europe,” etc. Further, a customerdemographic may describe descriptions of the customers that a merchanttargets. For example, a customer demographic may include, for example,“teenagers,” “wealthy,” “toddlers,” “construction workers,” “engineers,”etc. A customer demographic may, additionally or alternatively, indicatea targeted religious affiliation, gender, race, hobby, etc. of acustomer of a merchant. Even further, a merchant cost category maydescribe descriptions of how much goods or services cost at particularmerchant or how much they cost relative to similar merchants. Forexample, a merchant cost category may indicate that a merchant providesgood and/or services that are expensive, mid-range, or low in cost, orit may indicate that the goods and/or services are provided for a costthat is above-average, average, below-average, etc. to the costs ofsimilar merchants.

At step 515, financial service provider system 130 may determine a usersentiment for the merchant. Financial service provider system 130 maydetermine a user sentiment for the merchant in the current transactionby comparing the tip data of the current transaction to the historicaltip data. In some embodiments, financial service provider system 130 maynormalize the historical tip data (retrieved in step 505) beforecomparing the tip data of the current transaction to the historical tipdata. Financial service provider system 130 may normalize the historicaltip data in order to properly compare the tip of the current transactionto the historical tip data. For example, the tip data may be normalizedto reduce the impact of subjective factors in determining a usersentiment for the merchant, such as the user being a “good” or “bad”tipper. Financial service provider system 130, in some embodiments, maynormalize the historical tip data using a Gaussian distribution,Logistic distribution, etc.

To determine the user sentiment by comparing the tip data of the currenttransaction to the historical tip data, financial service providersystem 130 may determine the user sentiment based on what confidenceinterval, percentage, number, etc. that the current tip data is withinthe normalized historical tip data. For illustrative purposes only,financial service provider system 130 may define the user sentiment asan above-average rating if the tip data of the current transaction lieswithin any percentile above the 50^(th) percentile of the normalizedhistorical tip data and as below-average if the tip data of the currenttransaction lies within any percentile below the 50^(th) percentile ofthe normalized historical tip data. At step 520, financial serviceprovider system 130 may normalize the merchant review data (retrieved instep 415). In some embodiments, the historical tip data may benormalized using a Gaussian distribution, Logistic distribution, etc.

At step 525, financial service provider system 130 may adjust themerchant review data based on the user sentiment. Financial serviceprovider system 130 may determine the overall sentiment based on thenormalized merchant review data. For example, financial service providersystem 130 may determine the overall sentiment using a weighted averageof each set of information in the normalized merchant review data (e.g.,each tip) with its corresponding percentile. In some embodiments,financial service provider system 130 may use the user sentiment in theweighted formula in step 525 to adjust the overall sentiment.Additionally or alternatively, financial service provider system 130 mayvalue certain characteristics, such as the most recent tip data, etc.Financial service provider system 130 may express its valuing of thesecharacteristics in its weighted average formula. In various embodiments,financial service provider system 130 may use other techniques to adjustmerchant review data, such as incorporating user sentiment into anaveraging formula, logical model, machine learning model, etc. using thenormalize or non-normalize merchant review data.

Turning back to FIG. 4, financial service provider system 130 mayprovide the modified merchant review data to user device 110, merchantdevice 120, consumer device 140, etc. (step 425). Financial serviceprovider system 130 may provide the modified merchant review data via anAPI. In some embodiments, financial service provider system 130 mayprovide the modified data to the entity (e.g., device, system, etc.)from which financial service provider system 130 retrieved the merchantreview data in step 415.

FIG. 6 is a flowchart of an exemplary merchant review capturing process600, consistent with disclosed embodiments. In some embodiments,financial service provider system 130 may perform some or all of thesteps of process 600. In certain embodiments, other components of systemenvironment 100 (e.g., user device 110, merchant system 120, consumersystem 140, etc.) may perform one or more steps of process 600. Forsimplicity, process 600 will be described below as being performed byfinancial service provider system 130. Process 600 is similar to process400. However, process 600, unlike process 400, may be initiated byreceiving a request from consumer system 140. Process 600 is onlyprovided to illustrate one of the various processes covered by thepresent disclosure.

At step 605, financial service provider system 130 may receive a requestfrom one or more consumer systems 140. Consumer system 140 may beassociated with a website (or a server, database, API, etc.) that offersreviews for various merchants. In some embodiments, the request mayindicate one or more merchants for which consumer 140 may wish to obtainupdated individual or overall merchant reviews. After receiving therequest or in response to receiving the request, financial serviceprovider system 130 may retrieve authorization data (at step 610) and/orretrieve posted transaction data (at step 615). For example, financialservice provider device 130 may retrieve the authorization data and/orposted transaction data from database 160, cloud service 170, memory330, an external API, an external server, an external database, or thelike.

Financial service provider system 130 may retrieve merchant review data(at step 620) using techniques described above in relation to steps 415,610, and/or 615. In some embodiments, financial service provider system130 may retrieve merchant review data based on the request sent at step605. Financial service provider system 130 may, additionally oralternatively, retrieve merchant review data from consumer system 140 bysending a request to consumer system 140. In certain embodiments,financial service provider system 130 may modify merchant review data(at step 625) and provide the modified merchant review data to consumersystem 140 (at step 630) using similar techniques to those describedabove in relation to steps 420 and 425, respectively.

FIG. 7 is a flowchart of an exemplary recommendation provisioningprocess 700, consistent with disclosed embodiments. In some embodiments,financial service provider system 130 may perform some or all of thesteps of process 700. In certain embodiments, other components of systemenvironment 100 (e.g., user device 110, merchant system 120, consumersystem 140, etc.) may perform one or more steps of process 700. Forsimplicity, process 700 will be described below as being performed byfinancial service provider system 130.

At step 705, financial service provider system 130 may receive anindication to provide a recommendation to a user (i.e., target user).Financial service provider system 130 may receive the indication toprovide the recommendation to the target user from user device 110and/or another device (e.g., such merchant device 120). Moreover,financial service provider system 130 may receive the indication toprovide the recommendation from a user device associated with anotheruser. In some embodiments, the other user may be associatedprogrammatically (e.g., as a friend, associate, family member, businesspartner, etc.) with the target user. In some embodiments, financialservice provider system 130 may receive an indication to provide therecommendation by detecting that a user device (e.g., user device 110)associated with the target user is within a zone associated with amerchant and/or a merchant attribute. For example, financial serviceprovider system 130 may receive location data (e.g., GPS data) from userdevice 110 and determine that user device 110 is within a zoneassociated with five-star restaurants, low costs merchants, etc. Asanother example, financial service provider system 130 may receivelocation data (e.g., GPS data) from user device 110 and determine thatuser device 110 is within a zone associated with a merchant location. Todetermine the whether user device 110 is within the zone, financialservice provider system 130 may use techniques such as geo-fencing.

In some embodiments, financial service provider system 130 may determinea geofence, that is, one or more vertices and/or points surrounding ageographic area associated with a merchant location and/or merchantattribute. For example, financial service provider system 130 maydetermine a geofence associated with fine dining restaurants (i.e. themerchant attribute denoted as service type) located in a particulargeographic areas. Financial service provider system 130 may look upcoordinates by using device location data, database 240, and/or cloudservice 250. For example, financial service provider system 130 may lookup vertices that define the boundary of a geofence associated with amerchant location and/or merchant attribute; points that define theboundary of a geofence associated with a merchant location and/ormerchant attribute; an equation that defines the boundary of a geofenceassociated with a merchant location and/or merchant attribute; or thelike; or any combination thereof. In certain embodiments, financialservice provider system 130 may determine a geofence that is associatedwith a merchant location by using an API.

After financial service provider system 130 has determined a geofencethat is associated with a merchant location, financial service providersystem 130 may then determine whether the device location dataassociated with user device 110 are within the geofence. In someembodiments, financial service provider system 130 may not require thatall of the device location data to be within the geofence but mayrequire only that a predetermined number or percentage of the devicelocation data is within the geofence. In some embodiments, if less thana predetermined number or percentage of device location data is withinthe geofence, financial service provider system 130 may acquireadditional device location data. In some embodiments, the financialservice provider system 130 may determine a higher individual merchantconfidence rating based on detecting that user device 110 has been inthe geofence for a longer predetermined period of time.

At step 710, financial service provider system 130 may retrievehistorical tip data for the target user (e.g., a user associated withuser device 110) and, at step 715, financial service provider system 130may retrieve historical tip data for other users. Financial serviceprovider system 130 may retrieve historical tip data for the user andother users using techniques similar to those described in relation tostep 505. In some embodiments, financial service provider system 130 mayretrieve historical tip data for other users based on a zone associatedwith a merchant and/or a merchant attribute that the user device isdetected within, as described above in step 705.

At step 720, financial service provider system 130 may determinehistorical tip data of other users (retrieved at step 710) that isrelated to historical tip data of the target user (retrieved at step705). Financial service provider system 130 may determine thathistorical tip data of another user is related to historical tip data ofthe target user by calculating a commonality score that representscommon attributes between the users and, optionally, comparing thecommonality score to a threshold commonality score. In some embodiments,the commonality score is calculated using an algorithm based on weightedfactors. For instance, a commonality score may be a percentage or numberthat represents common interests between the users, for examplerepresenting that one of the other users and the target user both liketo attend fine dining restaurants, tip nearly the same amount at finedining restaurants, and love attending fine dining restaurants in thesummer. In some embodiments, the commonality score is calculated basedon data extracted from merchant attributes included in historical tipdata or other transaction data (such as a time stamp or date stamp forthe receipt the tip data was extracted from). In some embodiments,calculating the commonality score may be based on factors representingcommonalities between merchant attributes included in historical tipdata of other users and merchant attributes included in the historicaltip data of the target user. For example, the commonality score may berepresented as one or more vectors. Each vector component may representa different merchant attribute. Moreover, for example, the commonalityscore may be represented as a weighted average, where each similarity ordifference between users may be weighted by one or more factors. Forexample, the similarity or difference between the users may be based onfactors representing user attributes (such as common interests,demographics, etc.) or merchant attributes. In some embodiments, theuser attributes and merchant attributes may be extracted from historicaltip data. In some embodiments, calculating the commonality score may bebased on commonalities between user attributes and/or merchantattributes represented by a model. For example, financial serviceprovider system 130 may calculate the commonality score using a modelthat extracts attributes from various merchants to determine thesimilarities between the merchants, and extracts attributes from theusers to determine the similarities between the users. The model may bea logical model or machine learning model, as discussed above withrespect to adjusting merchant review data.

At step 725, financial service provider system 130 may determine arecommendation for the target user based on the related historical tipdata of other users and the target user. In some embodiments, financialservice provider system 130 may normalize one or more tip amounts fromthe historical tip data of the target user and normalize one or more tipamounts from the historical tip data of the other users. In someembodiments, financial service provider system 130 may normalize the oneor more tip amounts using similar techniques to those described in step515.

The financial service provider system 130 may compare the normalized tipamounts to determine a match. For example, using the normalized tipamounts, financial service provider system 130 may determine historicaltip data with the closest match between the normalized tip data of thetarget user and the normalized tip data of the other users. In someembodiments, the match may be represented by a confidence score. Forexample, the financial service provider system 130 may calculate aconfidence score, which may be a number or percentage, representing thematch between the normalized tip amounts. In some embodiments, thefinancial service provider system 130 may compare the calculatedconfidence score to a threshold score to determine the closest match.Based on the closest match, financial service provider system 130 maydetermine a recommendation based on the historical tip data associatedwith the closest match, In some embodiments, financial service providersystem 130 may determine to recommend the merchant identified inhistorical tip data associated with the closest match to the user. Insome embodiments, the recommendation may be further based on additionalfactors, such as data received from the user device. For example, thefinancial service provider system 130 may detect that user device 110has been in the geofence for a longer predetermined period of time, andfurther base the recommendation on this data point.

At step 730, financial service provider system 130 may provide therecommendation to the target user. Financial service provider system 130may provide the recommendation to the target user, for example, byproviding the recommendation to user device 110, merchant device 120,consumer system 140, and/or the like.

In some embodiments, financial service provider system 130 may seek tofigure out and learn from the recommendation provided at step 730. Atstep 735, financial service provider system 130 may retrieveauthorization data (using techniques similar to those described in 405)and/or, at step 740, retrieve posted transaction data (using techniquessimilar to those described in 410). Financial service provider system130 may complete steps 735 and 740 after the target user makes apurchase at a merchant.

At step 745, financial service provider system 130 may determine aneffectiveness of the recommendation (e.g., the recommendation providedat step 730) In some embodiments, financial service provider system 130may determine the effectiveness of the recommendation by determining theuser sentiment that the target user has for the merchant based on theauthorization data and posted transaction data (using techniques similarto those described in 510). For example, if the user sentiment indicatesthat the target user provided an above-average tip (or the usersentiment is above-average) to the merchant, financial service providersystem 130 may determine that the recommendation was highly effective.On the other hand, if the target user provided a below-average tip (orthe user sentiment is below average) to the merchant, financial serviceprovider system 130 may determine that the recommendation was noteffective.

In certain embodiments, financial service provider system 130 maydetermine an effectiveness of the recommendation by querying the targetuser. For example, financial service provider system 130 may provide, tothe user device, a request to obtain an effectiveness of therecommendation, receive a response to the request indicating theeffectiveness of the recommendation and determine the effectiveness ofrecommendation from the response.

At step 750, financial service provider system 130 may save thedetermined effectiveness of the recommendation. In some embodiments,financial service provider system 130 may use the saved determinedeffectiveness when determining a future recommendation for the targetuser or another target user. For example, financial service providersystem 130 may adjust the commonality score to weigh a merchantattribute more favorably if the recommendation is determined to behighly effective and/or weigh a merchant attribute less favorably if therecommendation is determined to be not effective. As another example,financial service provider system 130 may use the saved determinedeffectiveness as an additional input into a model that calculates thecommonality score (such as the logical model or machine learning modeldisclosed above). For example, the saved determined effectiveness may beused as an input to a reinforcement machine learning model to provide amore accurate and useful commonality score.

At step 755, financial service provider system 130 may provide thedetermined effectiveness of the recommendation to a merchant deviceassociated with the recommended merchant. Financial service providersystem 130 may provide this information to the recommended merchant sothat he merchant may improve its goods and/or services.

The described techniques may be varied and are not limited to theexamples or descriptions provided. In some examples, applications may bedeveloped for download to mobile communications and computing devices,e.g., laptops, mobile computers, tablet computers, smartphones, etc.,and made available for download by the user either directly from thedevice or through a website. In some embodiments, some or all of thelogic for the above-described techniques may be implemented as acomputer program or application or as a plug-in module or sub-componentof another application.

Moreover, while illustrative embodiments have been described herein, thescope thereof includes any and all embodiments having equivalentelements, modifications, omissions, combinations (e.g., of aspectsacross various embodiments), adaptations and/or alterations as would beappreciated by those in the art based on the present disclosure. Forexample, the number and orientation of components shown in the exemplarysystems may be modified. Further, with respect to the exemplary methodsillustrated in the attached drawings, the order and sequence of stepsmay be modified, and steps may be added or deleted.

Thus, the foregoing description has been presented for purposes ofillustration. It is not exhaustive and is not limiting to the preciseforms or embodiments disclosed. Modifications and adaptations will beapparent to those skilled in the art from consideration of thespecification and practice of the disclosed embodiments. For example,while a financial service provider has been described herein as theentity generating, providing, managing, and/or providing managing tipdata to provide reviews for one or more merchants, it is to beunderstood that, consistent with disclosed embodiments, another entitymay provide such services in conjunction with, or separate from, afinancial service provider.

The claims should be interpreted broadly based on the language employedin the claims and not limited to examples described in the presentspecification. Accordingly, the examples presented herein are to beconstrued as non-exclusive. Further, the steps of the disclosed methodsmay be modified in any manner, including by reordering steps and/orinserting or deleting steps.

Furthermore, although aspects of the disclosed embodiments are describedas being associated with data stored in memory and other tangiblecomputer-readable storage mediums, one skilled in the art willappreciate that these aspects can also be stored on and executed frommany types of tangible computer-readable media, such as secondarystorage devices, like hard disks, floppy disks, or CD-ROM, or otherforms of RAM or ROM. Accordingly, the disclosed embodiments are notlimited to the above-described examples but, instead, are defined by theappended claims in light of their full scope of equivalents.

1-20. (canceled)
 21. A system comprising: one or more memory devicesstoring instructions; and one or more processors configured to executeinstructions to perform operations comprising: receiving, from a userdevice associated with a user, an indication to provide a recommendationrequest for a merchant; determining, in response to receiving theindication, a location of the user device; retrieving, from a database,historical tip data associated with the user, the historical tip datacomprising historical tip amounts; retrieving, from the database,historical tip data associated with other users based on the determinedlocation, the historical tip data comprising historical tip amounts;calculating a commonality score representing common attributes betweenthe user and the other users; determining historical tip data associatedwith other users that is related to historical tip data of the userbased on the commonality score; normalizing the historical tip dataassociated with the user and the determined historical tip dataassociated with other users; determining a match between the normalizedhistorical tip data associated with the user and the normalizeddetermined historical tip data associated with other users; determininga recommendation for a recommended merchant based on the match; andtransmitting an electronic message comprising the recommendation to theuser device.
 22. The system of claim 21, wherein the location is withina geographic zone associated with one or more merchant attributes. 23.The system of claim 21, wherein the operation for determining historicaltip data associated with other users that is related to historical tipdata of the user based on the commonality score comprises: comparing thecalculated commonality score to a first threshold; and determininghistorical tip data associated with other users is related to historicaltip data of the user when the commonality score is above the firstthreshold.
 24. The system of claim 21, wherein the historical tip datacomprises merchant attributes associated with the historical tipamounts.
 25. The system of claim 24, wherein the merchant attributescomprise at least one of a merchant category, a merchant rating, amerchant location, a merchant location category, a merchant geographiccategory, a merchant cost category, or a merchant customer description.26. The system of claim 25, wherein the commonality score is calculatedbased on commonalities among merchant attributes included in historicaltip data.
 27. The system of claim 25, wherein the merchant attributesare extracted from historical tip data using a machine learning model.28. The system of claim 21, wherein the historical tip data associatedwith the user and the determined historical tip data associated withother users is normalized using a Gaussian distribution.
 29. The systemof claim 21, wherein the operation for determining a match furthercomprises: comparing the normalized historical tip data associated withthe user and the normalized determined historical tip data associatedwith other users; and determining a percentage match based on thecomparison.
 30. The system of claim 29, wherein the operation fordetermining a recommendation further comprises: determining arecommendation for the recommended merchant when the percentage matchexceeds a second threshold.
 31. The system of claim 21, wherein theoperations further comprise: determining that the user completed atransaction at a merchant system of the recommended merchant; anddetermining an effectiveness of the recommendation.
 32. The system ofclaim 31, wherein the operations for determining an effectiveness of therecommendation further comprise: receiving, from the merchant system,authorization data, the authorization data associated with thetransaction; receiving, from the merchant system, posted transactiondata, the posted transaction data corresponding to the authorizationdata; determining a tip amount associated with the transaction based onthe authorization data and the posted transaction data; and determininga user sentiment value for the recommended merchant based on thedetermined tip amount and the normalized historical tip data associatedwith the user, the user sentiment value representing a user sentimentfor the recommended merchant.
 33. The system of claim 31, wherein theoperations for determining an effectiveness of the recommendationfurther comprise: transmitting an electronic message comprising a surveyto the user device, the survey querying a user satisfaction with therecommendation; and receiving a response to the survey.
 34. A systemcomprising: one or more memory devices storing instructions; and one ormore processors configured to execute instructions to perform operationscomprising: determining that a user device associated with a user islocated within a geographic zone; receiving, based on the determination,an indication from the user device to provide a recommendation requestfor a merchant; retrieving, from a database, historical tip dataassociated with the user, the historical tip data comprising historicaltip amounts; retrieving, from the database, historical tip dataassociated with other users, the historical tip data comprisinghistorical tip amounts; calculating a commonality score representingcommon attributes between the user and the other users; determininghistorical tip data associated with other users that is related tohistorical tip data of the user based on the commonality score;normalizing the historical tip data associated with the user and thedetermined historical tip data associated with other users; determininga match between the normalized historical tip data associated with theuser and the normalized determined historical tip data associated withother users; determining a recommendation for a recommended merchantbased on the match; and transmitting an electronic message comprisingthe recommendation to the user device.
 35. The system of claim 34,wherein the geographic zone is associated with at least one of amerchant category, a merchant location, a merchant geographic category,or a merchant cost category.
 36. The system of claim 34, wherein thehistorical tip data comprises merchant attributes associated with thehistorical tip amounts.
 37. The system of claim 34, wherein thehistorical tip data comprises merchant attributes associated with thehistorical tip amounts and the commonality score is calculated based oncommonalities among merchant attributes included in historical tip data.38. The system of claim 34, wherein the operation for determining amatch further comprises: comparing the normalized historical tip dataassociated with the user and the normalized determined historical tipdata associated with other users; and determining a percentage matchbased on the comparison.
 39. The system of claim 38, wherein theoperation for determining a recommendation further comprises:determining a recommendation for the recommended merchant when thepercentage match exceeds a second threshold.
 40. A system comprising:one or more memory devices storing instructions; and one or moreprocessors configured to execute instructions to perform operationscomprising: receiving, from a user device associated with a user, anindication to provide a recommendation request for a merchant;determining, in response to receiving the indication, a location of theuser device; retrieving, from a database, historical tip data associatedwith the user, the historical tip data comprising historical tipamounts; retrieving, from the database, historical tip data associatedwith other users based on the determined location, the historical tipdata comprising historical tip amounts; calculating a commonality scorerepresenting common attributes between the user and the other users;determining historical tip data associated with other users that isrelated to historical tip data of the user based on the commonalityscore; determining a match between the historical tip data associatedwith the user and the determined historical tip data associated withother users; determining a recommendation for a recommended merchantbased on the match; transmitting an electronic message comprising therecommendation to the user device; determining that the user completed atransaction at a merchant system based on the recommendation, themerchant system being associated with the recommended merchant; andtransmitting an electronic message comprising a survey to the userdevice, the survey querying a user satisfaction with the recommendation.